librdkafka: expose retry and reconnect backoff settings #33973
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Exposes librdkafka settings as system settings:
retry.backoff.msretry.backoff.max.msreconnect.backoff.msreconnect.backoff.max.msMZ will provide the default values, most of which are set based on the current defaults described here.
I increased the default value for
reconnect.backoff.max.msto30sbased on local testing.librdkafkawould have tried reconnecting a few times quickly before reaching the30stime. If those didn't work, it's likely that the cause is longer lived. Happy to set this to the librdkafka default of10sif folks disagree.Motivation
exposes settings to help alleviate https://github.com/MaterializeInc/database-issues/issues/9801
Checklist
$T ⇔ Proto$Tmapping (possibly in a backwards-incompatible way), then it is tagged with aT-protolabel.